Download Upgrading Your Skills to MCSA: Windows Server 2016.70-743.PracticeTest.2017-07-05.103q.vcex

Windows Server 2016 Domain controller is required for Device Registration for Servers that run Windows Server 2016. References: https://technet.microsoft.com/en-us/windows-server-docs/identity/adfs/operations/configure-device-based-conditional-access-on-premises

Publish an Integrated Windows authenticated-based Application for Web Browser Clients Step 1: (configure the Backend server SPN – see first bulleted item below)Before you begin, make sure that you have done the following:* Made sure that the Web Application Proxy servers are configured for delegation to the service principal names (SPN) of the backend servers. * Created a non-claims-aware relying party trust for the application in the AD FS Management console. * Configured the backend server to support Kerberos constrained delegation on the domain controller or by using the Set-ADUser cmdlet with the -PrincipalsAllowedToDelegateToAccount parameter. Note that if the backend server is running on Windows Server 2012 R2 or Windows Server 2012, you can also run this PowerShell command on the backend server. * Verified that a certificate on the Web Application Proxy server is suitable for the application you want to publish. Step 2: http//server2.contoso.com/publish/app1Use the same URL as the backend server URL. Web Application Proxy can translate host names in URLs, but cannot translate path names. Therefore, you can enter different host names, but you must enter the same path name. For example, you can enter an external URL of https://apps.contoso.com/app1/ and a backend server URL of http://app-server/app1/. However, you cannot enter an external URL of https://apps.contoso.com/app1/ and a backend server URL of https://apps.contoso.com/internal-app1/.References: https://technet.microsoft.com/en-us/library/dn383640(v=ws.11).aspx

Windows Server 2016 Domain controller is required for Device Registration for Servers that run Windows Server 2016. References: https://technet.microsoft.com/en-us/windows-server-docs/identity/ad-fs/operations/configure-device-based-conditional-access-on-premises

Deploy Network Controller using Windows PowerShell Step 1: Install-WindowsFeatureInstall the Network Controller server role To install Network Controller by using Windows PowerShell, type the following commands at a Windows PowerShell prompt, and then press ENTER. Install-WindowsFeature -Name NetworkController –IncludeManagementTools Step 2: New-NetworkControllerNodeObjectYou can create a Network Controller cluster by creating a node object and then configuring the cluster. You need to create a node object for each computer or VM that is a member of the Network Controller cluster. To create a node object, type the following command at the Windows PowerShell command prompt, and then press ENTER. Ensure that you add values for each parameter that are appropriate for your deployment. New-NetworkControllerNodeObject –Name <string> -Server <String> -FaultDomain <string>-RestInte Step 3: Install-NetworkControllerClusterTo configure the cluster, type the following command at the Windows PowerShell command prompt, and then press ENTER. Ensure that you add values for each parameter that are appropriate for your deployment. Install-NetworkControllerCluster –Node <NetworkControllerNode[]> –ClusterAuthentication … Step 4: Install-NetworkControllerTo configure the Network Controller application, type the following command at the Windows PowerShell command prompt, and then press ENTER. Ensure that you add values for each parameter that are appropriate for your deployment. Install-NetworkController –Node <NetworkControllerNode[]> –ClientAuthentication References: https://technet.microsoft.com/en-us/library/mt282165.aspx

Using Windows PowerShell, the REST API, or a management application, you can use Network Controller to manage the following physical and virtual network infrastructure:* Datacenter Firewall This Network Controller feature allows you to configure and manage allow/deny firewall Access Control rules for your workload VMs for both East/West and North/South network traffic in your datacenter. The firewall rules are plumbed in the vSwitch port of workload VMs, and so they are distributed across your workload in the datacenter. Using the Northbound API, you can define the firewall rules for both incoming and outgoing traffic from the workload VM. You can also configure each firewall rule to log the traffic that was allowed or denied by the rule. * Hyper-V VMs and virtual switches * Remote Access Service (RAS) Multitenant Gateways, Virtual Gateways, and gateway pools * Load Balancers References: https://technet.microsoft.com/en-us/library/dn859239.aspx

If the container host is virtualized, and you wish to use DHCP for IP assignment, you must enable MACAddressSpoofing. PS C:\> Get-VMNetworkAdapter -VMName ContainerHostVM | Set-VMNetworkAdapter -MacAddressSpoofing OnThe command needs to be run on the Hyper-V host. References: https://msdn.microsoft.com/en-us/virtualization/windowscontainers/management/container_networking

Configure Docker with Configuration File The preferred method for configuring the Docker Engine on Windows is using a configuration file. The configuration file can be found at 'c:\ProgramData\docker\config\daemon.json'.Only the desired configuration changes need to be added to the configuration file. For example, this sample configures the Docker Engine to accept incoming connections on port 64500. All other configuration options will use default values. { "hosts": ["tcp://0.0.0.0:64500"]} References: https://msdn.microsoft.com/en-us/virtualization/windowscontainers/docker/configure_docker_daemon

Do you have a large number of virtualized workloads in your cluster? Have you been looking for a solution that allows you to detect if any of the virtualized workloads in your cluster are behaving abnormally? Would you like the cluster service to take recovery actions when these workloads are in an unhealthy state? In Windows Server 2012/2016, there is a great new feature, in Failover Clustering called “VM Monitoring”, which does exactly that – it allows you monitor the health state of applications that are running within a virtual machine and then reports that to the host level so that it can take recovery actions. VM Monitoring can be easily configured using the Failover Cluster Manager through the following steps:Right click on the Virtual Machine role on which you want to configure monitoring Select “More Actions” and then the “Configure Monitoring” options You will then see a list of services that can be configured for monitoring using the Failover Cluster Manager. References: https://blogs.msdn.microsoft.com/clustering/2012/04/18/how-to-configure-vm-monitoring-in-windows-server-2012/

The disks used in Storage Spaces Direct cannot contain existing partitions.

If you have decided to use Kerberos to authenticate live migration traffic, configure constrained delegation before you proceed to the rest of the steps. To configure constrained delegation Open the Active Directory Users and Computers snap-in. From the navigation pane, select the domain and double-click the Computers folder. From the Computers folder, right-click the computer account of the source server and then click Properties. In the Properties dialog box, click the Delegation tab. On the delegation tab, select Trust this computer for delegation to the specified services only. Under that option, select Use Kerberos only.